Method for optimizing quality of experience in mixed managed and unmanaged network environments with governance and regulation constraints

ABSTRACT

This invention makes media routing decisions within a distributed communications system that spans both managed and unmanaged networks, while taking into account a large set of input metrics. It is meant to optimize for quality of experience while maintaining restrictions posed by companies and organizations who need to adhere to strict policies, either internal or external such as governance and regulation.

BACKGROUND OF THE INVENTION

In the domain of WebRTC, there are many solutions developed in cloud environments. The main concern and consideration there is optimizing for call quality, routing media through the closest media relay points (closest being based on network topology and not necessarily geographically). For regulated industries or enterprises seeking higher security levels, compliance with regulations and corporate governance, this may not be the case.

Existing solutions fail to take into considerations scenarios where the speakers' call must be recorded and stored at a specific location or country, or when the sensitivity or context of the call needs to be governed or analyzed for specific content.

To that end, we have invented a new algorithm designed to work for routing media where a more complex decision process needs to be made regarding the relay and routing points. These decision processes need to take into consideration data retention, governance, regulation and call quality—as well as other aspects of the call.

BRIEF SUMMARY OF THE INVENTION

The present invention is an algorithm that makes a decision on the best way to connect a chat, voice or video call between two or more users in a communication system. Where “best way” is dependent on multiple variables, such as the users' location, the user's role, the device's characteristics, the location of the offices and other characteristics that relate to the geography, location, regulations, types of users that participate in the communication, method of communication, connectivity bearer, device and enterprise and other corporate settings.

The invention ensures calls adhere to the legal environment, compliance, corporate governance and regulations they must operate in, while maintaining high level of user experience and serviceability to the users of the communication system.

The present invention provides a method for routing a call initiated by at least one member of an organization having at least one communication server for handling the call routing, wherein the organization communication server are located at different geographical areas. The method comprising the steps of:

-   -   Receiving call request with metadata of requesting device and         requesting member;     -   Identifying geographical and logical location of requesting         member and call destination based on received meta data;     -   Authorizing call based on determined location, metadata by         applying organization policy; and     -   Determining call routing method based on location data and         metadata by applying pre-defined organization policies rules.

According to some embodiments of the present invention the call routing method is at least one of: local routing using single network server, non-local routing using more than one designated server or P2P call routing.

According to some embodiments of the present invention determining of call routing include determining routing path based call session quality parameters.

According to some embodiments of the present invention determining of call routing include determining call type

According to some embodiments of the present invention the quality parameters are tested using organization servers or cloud servers. (Consulting with peer offices/cloud servers).

According to some embodiments of the present invention the method further comprising the step of determining additional actions including at least one of: monitoring, recording or encrypting of call session by at least one designated network server.

According to some embodiments of the present invention the meta data include at least one of: requesting user profile, requesting user device characteristics, connectivity profile or network quality.

According to some embodiments of the present invention the location identification is based on retrieving data of past interactions of user requests in short time period, in case of identifying call request as continuation of previous call maintaining the same routing method and path.

According to some embodiments of the present invention in case of local routing the routing is based on office location using a single network sever.

According to some embodiments of the present invention in case of non-local routing the routing is based on user location using more than one network server.

The present invention provides a system for routing a call initiated by at least one user of an organization having at least one communication server for handling the call routing, wherein the organization communication server are located at different geographical areas. The system is comprised of:

-   -   Location identifying module for identifying geographical and         logical location of requesting member based on received meta         data;     -   Authorizing module for authorizing call based on determined         location, metadata by applying organization policy; and     -   Routing decision module for determining call routing method         based on location data and metadata by applying pre-defined         organization policies rules.

According to some embodiments of the present invention the call routing method is at least one of: local routing using single designated network server, non-local routing using more than one server or P2P call routing.

According to some embodiments of the present invention determining of call routing include determining routing path based call session quality parameters.

According to some embodiments of the present invention determining of call routing include determine call type.

According to some embodiments of the present invention the quality parameters are tested using organization servers or cloud servers. (Consulting with peer offices/cloud servers).

According to some embodiments of the present invention routing decision module further determine actions to be taken in relation to the call including at least one of: monitoring, recording or encrypting of call session by at least one network server.

According to some embodiments of the present invention the location identification is based on Retrieving data of past interactions of user requests in short time period, in-case of detecting the new call request is a continuation of previous call maintaining the same routing method and path.

According to some embodiments of the present invention in case of local routing the routing is based on office location using a single network sever.

According to some embodiments of the present invention in case of non local routing the routing is based on user location using more than one network server.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates the system entities that play a role according to some embodiments of the present invention. The system entity comprises one or more offices, belonging to an organization, an optional external cloud service and users who connect to each other via devices.

FIG. 2 illustrates the gateway server (backend server) block diagram according to some embodiments of the present invention.

FIG. 3 illustrates the algorithm flow for call session initiation according to some embodiments of the present invention. It depicts how the Backend Server decides on the best routing strategy for each session dynamically based on multiple metrics and policies.

FIG. 4 is an illustration flow chart of the authorization module, according to some embodiments of the invention;

FIG. 5 is an illustration flow chart of the location identification module, according to some embodiments of the invention.

FIG. 6 is a diagram of the routing decision module, according to some embodiments of the invention.

FIG. 7 is an illustration flow chart of the local call establishing module, according to some embodiments of the invention.

FIG. 8 is an illustration flow chart, of the routing algorithm according to some embodiments of the preset invention.

DETAILED DESCRIPTION AND BEST MODE OF IMPLEMENTATION

The present invention is implemented in environment of an organization, having s a distributed communication system. This communication system is built out of one or more offices 100, 130, 140, along with an optional external cloud service 150.

According to some embodiment of the present invention an office may include different network zones, such as: a MZ (militarized zone) 110, where machines and servers are not exposed directly to an external network; and a DMZ (demilitarized zone) 120, where machines and servers are located at a perimeter network of the office, exposed to external untrusted networks.

In the DMZ 120, there can be one of more Frontend Servers 123. These servers take care of connecting the signals from devices 161, 171 located outside the office network into the servers located in the MZ 110.

In the DMZ 120, there can optionally be an SBC (Session Border Controller) 122, in charge of connecting all media and VoIP (Voice over IP) signaling from outside the office network into the office VoIP servers. SBCs are mainly used as security and interoperability mechanisms.

In the DMZ 120, there can optionally be one or more TURN servers 121. These servers are used to relay media traffic coming from WebRTC, SIP or any other protocols that make use of STUN or TURN IETF specifications. These servers ensure that media can be sent between the various users of the communication system without getting blocked by firewalls or NATs (Network Address Translators).

In the MZ 110, there is one or more Backend Servers 116. These servers take care of the core logic of the communication system, taking into account the authorized users who can make use of the communication system by working in concert with a Corporate Directory 113 and a Policy database 112, where all policy related rules and directives are stored. The Backend Server 116 also communicates with the Signaling server 115, directing it on the decisions made, effectively enforcing the policy desired by the organization.

In the MZ 110, there is one or more Signaling servers 115. These servers implement a known signaling protocol used across the communication system to communicate signals between devices and servers. This signaling protocol can be a standards based protocol such as SIP or XMPP, a proprietary protocol or a combination of protocols. The Signaling server communicates with the SBC 122, or directly with the devices 161, 171 in the case the devices are located within the local network (the MZ 110) or when an SBC 122 doesn't exist or isn't necessary for the specific communication session. The Signaling server 115 also communicates with the TURN Server 121 and the Media Router 114, directing them on how to operate for each and every communication session they engage in.

In the MZ 110, there is one or more Media Routers 114. These routers are in charge of opening any encryption and privacy mechanisms that are used to send the media over the network, as well as closing the encryption and privacy mechanisms when routing the media to other participants in the communication session. The Media Router 114 are considered a trusted entity in the system when it comes to the media, with the ability to listen in to the voice, video and any other rich content sent in the communication session. The Media Router 114 may communicate with external real time media system such as a Recording server 111, who are used to store or further process and analyze the media. An example of such other server can be a DPI (deep packet inspection) mechanism that analyzes the conversation, tracking files delivered, certain keywords and phrases; examines the video session, searching for specific artifacts and elements; analyze the conversation's tone or sentiment; etc.

Within an Office 100, the various server components can be merged to comprise fewer physical machines offering similar logical functions, the various server components can be further split into smaller functional units that together comprise of similar logical functions.

Within an Office 100, some of the servers and functions depicted can be disabled and removed from the architecture when the specific function is not needed. Recording 111, for example, is not mandated or required by some organizations.

There can be one or more Offices 100, 130, 140 that can be deployed as part of the communication network. There is no limit to the number of such offices. They are internally architected in a similar manner to the depiction of Office A 100. The offices may be located at different geographical areas and related to different part of the organization.

An optional Cloud Service 150 can also be used. It is architected in a similar manner to the depiction of Office A 100, though can be further distributed geographically as well as offer multi tenancy for several companies. The Cloud Service acts as another access point into the communication service that augments and optimizes the on premise communication service of the company or companies.

The invention enables the communication between the Users 160, 170 who access the communication network. These users can be humans or automated machines. They connect to the network and communicate with other Users 160, 170 through the use of Devices 161, 171. These Devices 161, 171 can be smartphones, tablets, laptops, computers, Internet of Things devices, wearables or any other computational device capable of network connectivity. The users may be located at different geographical areas and belong to different entities of the organization. Each entity of the organization may have different policies for routing.

When User A 160 wishes to connect to the communication system, he registers to it, as depicted in 200. This can take place by any means of communications—standards based or proprietary. It can take the form of a SIP REGISTER message, a social network connect procedure, OAuth transaction or any other alternative.

When User A 160 wishes to communicate with User B 170, he signals the Backend Server 116 about his intent, as depicted in 201. This can take the form of any means of communications—standards based or proprietary. It can take the form of a SIP INVITE message or any other alternative. User B 170 can be a single user or multiple users in a group session or a group conference.

When User A 160 reaches out to User B 170 via call initiation 201, it does so via its Device 161, notifying it of its intent and the destination of User B 170. The Device can add to this initiation request additional meta data to be used for call routing decisions. This additional meta data may or may not prompt User A 160 for his approval. The additional meta data may include the Device 161 location, based on its IP address, GPS coordinates, WiFi and cellular triangulation or other means of pinpointing the device. Additional meta data may include the Device 161 characteristics, such as model, make, CPU performance, memory, storage capacity, screen resolution or other characteristics. Additional meta data may include the Device 161 network information, such as user role, its connectivity profile, network quality or any other information that is deemed useful to making a decision. The additional meta data may include other types of information that may be needed for the policy decision making algorithm to make a more informed routing decision.

In 202, the Backend Server 116, receives the request along with the meta data from User A's Device 161. The message can be a single one, or multiple consecutive or parallel messages, and can be sent in any digital means. It can be sent directly to the Backend Server 116 or traverse through the Frontend Server 123 to ensure the network security policies in the organization are adhered. Once the request is received and authenticated by the Backend Server 116, it will initiate the algorithm to determine the best route to connect User A 160 to User B 170.

In 203, the Backend Server 116, calculates the location of User A 160. It does so by analyzing the network address of his Device 161, along with any supporting meta data and information sent by User A 160 in his request or in previous requests. The calculation of location will try to pinpoint the user's location geographically as well as find out its network location—inside the corporate managed network or outside of the corporate network, and the specific corporate Office 100 location. It then calculates the location of User B 170 by any information it has on it from past interactions or registration information sent by User B 170 to the Backend Server 116 or the Signaling Server 115.

In 204, the Backend Server 116 checks if the session requested by User A 160 is allowed. This can be based on User A 160 and User B 170 role, or other policies of the organization. For example, User A 160 may not be allowed to communicate with people external to the organization, or may not be allowed to communicate with people from other teams or with his superiors, or may not be allowed to make video calls while is allowed to make voice calls. Furthermore, this can be based on the users; location. For example, User A 160 may not be allowed to communicate with people while roaming outside of the corporate Office 100 or while traveling to certain countries.

In 204, if the Backend Server 116 determines that the call is not allowed, it will reject the session in 205 and notify User A 160 via its Device 161. This rejection and the test for session validity can take place later on in the algorithm as well, once more information about the session becomes available to the Backend Server 116.

In 210, the Backend Server 116 decided that this session is allowed. It further checks if local routing of the media is mandated which required routing the call through at least one designated communication/switching server. Such a routing policy may be forced due to various factors such as governance, regulation, session participants, recording and analysis requirements, etc.

The routing policy in 210 can decide to force routing 220 if the call is conducted to a customer or a partner for example (a non-employee), or if the role or position of User A 160 in the company is such that requires media routing. It may further decide to route the session (or not route it) if the specific media types (voice/video/other data) mandate such routing. It may further decide to route the session (or not route it) if the user is located inside a company Office premise be it Office A 100, Office B 130, Office C 140, some other office or connected via secured VPN. It can further decide to route the session (or not route it) based on the location of User A 160's Device 161, his Office A 100 and the regulatory or policy restriction of that location versus his office location. It may further decide to route the session if the session must be recorded (or further processed) via Archiving Server 111.

The routing policy in 210 is configurable and stored in the Policy 111 database. It is accessed by the Backend Server 116 whenever a routing decision is made, it can be cached locally by the Backend Server 116 to improve performance by learning the optimal routing path in different call scenarios.

If the Backend Server 116 decides in 210 that the session mandates local routing, then in 220, the Backend Server 116 will instruct the Signaling Server 115 (designated network sever)to prepare for routing the call locally. The Signaling Server 115 will authorize the Media Router 114, TURN server 121 and/or SBC 122 to allow the session to take place. The Signaling Server 115 will further prepare additional backend components such as Recording 111 to accept and process this session as needed.

If the Backend Server 116 decides in 210 that the session does not mandate local routing, then it goes on to decide if the session needs to be routed at all in 211.

In 211, the Backend Server 116 decides if the call must still be routed. This decision is based on routing policy as well as the session's requirements. The decision making process of 211 follows similar policy steps on currently available meta data outlined in paragraph [00029] and paragraph [00030].

If the Backend Server 116 decides in 211 that the session mandates routing in nonlocal route, then the Backend Server 116 will resolve to 221 in order to consult with its peers in other offices (B 130, C 140 or additional offices known and available to it) on the best suitable office to relay the media from. Backend Server 116 may also consult with a Cloud Service 150 in the same way that it would treat another office, assuming it is allowed by its own internal policies. The decision process taken here on the most suitable office to route the call through will take place into account the user's Device 161 location, as well as the location and routing policies known for the other participants in the session (if they are known).

If the Backend Server 116 decides in 211 that routing the session isn't mandated (not requiring designated server in the call rout), then it would continue to 212 and attempt peer-to-peer calling for this session, basing the decision on the user's location. To do that, the Backend Server 116 will consult with his peers in other offices (B 130, C 140 or additional offices known and available to it) on the best suitable office to provide TURN 121 services from. Backend Server 116 may also utilize the Cloud Service 150 in the same way that it would treat another office, assuming it is allowed by its own internal policies. The User A 160's Device 161 will then be instructed to attempt creating a session with User B 170's Device 171 directly, with the assistance of the relevant TURN Servers 121 that were picked for this session.

FIG. 2 illustrates the gateway server (backend server) block diagram according to some embodiments of the present invention. The backend server is comprised of modules implementing the logic of call session management and routing as suggested by some embodiments of the present invention. The first module 300 analyses call request metadata at the initial stage for determining if to authorize the call based on organization policies. In case the call is authorized the location identification module 400 is launched to determine geographical and logical location of the users devices based on call request data and previous call sessions of the user. Based on determined location the routing decision module 500, decides of the routing method of the call such as local call 20, nonlocal call 39 or P2P call 50, the type of call session and further actions to be applied in relation to the call session such as monitoring or recording the call session, encrypting all or determining call pricing.

FIG. 4 is an illustration flow chart of the authorization module, according to some embodiments of the invention. The processing of the authorization module comprises the following steps: receiving the call request along with the meta data from User A's Device 161 (step 310) including identification of the destination device; optionally receiving security confirmation from the front end server based on organization security policies (step 320); authenticating request based on request metadata (step 330) and initiating Location identification module (step 340).

FIG. 5 is an illustration flow chart of the location identification module, according to some embodiments of the invention. The processing of the location module comprises the following steps: analyzing the network address of the initiating call Device and meta data of the call request (step 410); identifying geographical location data of the device based on GPS meta data or cellular network data (step 420); identifying network location: inside/outside cooperate managed network (step 430); retrieving data of past interactions of user requests (step 440); Identifying geographical and logical address of call destination device based on previous calls, determining or calculating user geographical and logical location based on location meta data, past data, geographical and logical location of call destination and registration information (step 450).

FIG. 6 is a diagram of the routing decision module, according to some embodiments of the invention. The routing module receives a call requests along with Meta data from User A's Device 510, and activate the Call routing algorithm 516. The Call routing algorithm is further provided with the physical and logical location of the requesting device 512, call destination 514, and call requested type 15. The call routing algorithm then uses this information to determine type of call 520 (e.g. video call, conference call etc.), to establish Local call (where routing is based on user location) to establish non local call (where routing is based on office location) or to establish P2P call session. Optionally the algorithm determines recording, monitoring or encrypting call session based on all received metadata. The routing algorithm is consulting with peer office or cloud sever to optimize call routing by testing different call paths. At each phase of the decision routing, the call may be rejected based on the current available metadata.

FIG. 7 is an illustration flow chart of the local call establishing module, according to some embodiments of the invention. The process of the local call establishing module comprises the following steps: instruct the signaling server 115 to prepare for routing the call locally (step 610); the signaling server 115 will authorize the media router 114 (step 620), TURN server 121 and/or SBC 122 to allow the session to take place (step 630); signaling server 115 will further prepare additional backend components such as recording 111 to accept and process this session as needed (step 640);

FIG. 8 is an illustration flow chart, of the routing algorithm according to some embodiments of the preset invention. The process of the routing algorithm comprises the following steps: applying policy rules of organization on location data and received metadata (step 710), The policy rules may define different scenarios for different user profiles, characteristics of the call device, device network information, connectivity profile different offices or branches of the organization based on physical or logical location of users participating in the call, enabling the organization to apply the appropriate routing method for each scenario, ensuring optimal quality and security measurements.

In case of determining local routing scenario, using single designated network server in the rout, based on office location of the requesting user and call destination (step 720). In case of determining routing method of nonlocal routing, than using more than one designated network server based on requesting user location of the call destination (step 730).

When determining routing path (networks, server) based on organization policy, the routing algorithm consult with peer offices or cloud servers checking call session availability or quality through different routes (step 740).

In case no designated server is required in rout, determining routing method of P2P protocol (step 750). The routing algorithm further determines call session type: video, conference (step 760 and determining additional action during call: recording, monitoring, or encryption (step 770).

The system of the present invention may include, according to certain embodiments of the invention, machine readable memory containing or otherwise storing a program of instructions which, when executed by the machine, implements some or all of the apparatus, methods, features and functionalities of the invention shown and described herein. Alternatively or in addition, the apparatus of the present invention may include, according to certain embodiments of the invention, a program as above which may be written in any conventional programming language, and optionally a machine for executing the program such as but not limited to a general purpose computer which may optionally be configured or activated in accordance with the teachings of the present invention. Any of the teachings incorporated herein may wherever suitable operate on signals representative of physical objects or substances.

Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that throughout the specification discussions, utilizing terms such as, “processing”, “computing”, “estimating”, “selecting”, “ranking”, “grading”, “calculating”, “determining”, “generating”, “reassessing”, “classifying”, “generating”, “producing”, “stereo-matching”, “registering”, “detecting”, “associating”, “superimposing”, “obtaining” or the like, refer to the action and/or processes of a computer or computing system, or processor or similar electronic computing device, that manipulate and/or transform data represented as physical, such as electronic, quantities within the computing system's registers and/or memories, into other data similarly represented as physical quantities within the computing system's memories, registers or other such information storage, transmission or display devices. The term “computer” should be broadly construed to cover any kind of electronic device with data processing capabilities, including, by way of non-limiting example, personal computers, servers, computing system, communication devices, processors (e.g. digital signal processor (DSP), microcontrollers, field programmable gate array (FPGA), application specific integrated circuit (ASIC), etc.) and other electronic computing devices.

The present invention may be described, merely for clarity, in terms of terminology specific to particular programming languages, operating systems, browsers, system versions, individual products, and the like. It will be appreciated that this terminology is intended to convey general principles of operation clearly and briefly, by way of example, and is not intended to limit the scope of the invention to any particular programming language, operating system, browser, system version, or individual product.

It is appreciated that software components of the present invention including programs and data may, if desired, be implemented in ROM (read only memory) form including CD-ROMs, EPROMs and EEPROMs, or may be stored in any other suitable typically non-transitory computer-readable medium such as but not limited to disks of various kinds, cards of various kinds and RAMs. Components described herein as software may, alternatively, be implemented wholly or partly in hardware, if desired, using conventional techniques. Conversely, components described herein as hardware may, alternatively, be implemented wholly or partly in software, if desired, using conventional techniques.

Included in the scope of the present invention, inter alia, are electromagnetic signals carrying computer-readable instructions for performing any or all of the steps of any of the methods shown and described herein, in any suitable order; machine-readable instructions for performing any or all of the steps of any of the methods shown and described herein, in any suitable order; program storage devices readable by machine, tangibly embodying a program of instructions executable by the machine to perform any or all of the steps of any of the methods shown and described herein, in any suitable order; a computer program product comprising a computer useable medium having computer readable program code, such as executable code, having embodied therein, and/or including computer readable program code for performing, any or all of the steps of any of the methods shown and described herein, in any suitable order; any technical effects brought about by any or all of the steps of any of the methods shown and described herein, when performed in any suitable order; any suitable apparatus or device or combination of such, programmed to perform, alone or in combination, any or all of the steps of any of the methods shown and described herein, in any suitable order; electronic devices each including a processor and a cooperating input device and/or output device and operative to perform in software any steps shown and described herein; information storage devices or physical records, such as disks or hard drives, causing a computer or other device to be configured so as to carry out any or all of the steps of any of the methods shown and described herein, in any suitable order; a program pre-stored e.g. in memory or on an information network such as the Internet, before or after being downloaded, which embodies any or all of the steps of any of the methods shown and described herein, in any suitable order, and the method of uploading or downloading such, and a system including server/s and/or client/s for using such; and hardware which performs any or all of the steps of any of the methods shown and described herein, in any suitable order, either alone or in conjunction with software. Any computer-readable or machine-readable media described herein is intended to include non-transitory computer- or machine-readable media.

Any computations or other forms of analysis described herein may be performed by a suitable computerized method. Any step described herein may be computer-implemented. The invention shown and described herein may include (a) using a computerized method to identify a solution to any of the problems or for any of the objectives described herein, the solution optionally include at least one of a decision, an action, a product, a service or any other information described herein that impacts, in a positive manner, a problem or objectives described herein; and (b) outputting the solution.

The scope of the present invention is not limited to structures and functions specifically described herein and is also intended to include devices which have the capacity to yield a structure, or perform a function, described herein, such that even though users of the device may not use the capacity, they are, if they so desire, able to modify the device to obtain the structure or function.

Features of the present invention which are described in the context of separate embodiments may also be provided in combination in a single embodiment.

For example, a system embodiment is intended to include a corresponding process embodiment. Also, each system embodiment is intended to include a server-centered “view” or client centered “view”, or “view” from any other node of the system, of the entire functionality of the system, computer-readable medium, apparatus, including only those functionalities performed at that server or client or node. 

1. A method for routing a call initiated by at least one member of an organization having at least one communication server for handling the call routing, wherein the organization communication server are located at different geographical areas, said method comprising the steps of: Receiving call request with metadata of requesting device and requesting member; Identifying geographical and logical location of requesting member and call destination based on received meta data; Authorizing call based on determined location, metadata by applying organization policy; and Determining call routing method based on location data and metadata by applying pre-defined organization policies rules.
 2. The method of claim 1 wherein the call routing method is at least one of: local routing using single network server, non-local routing using more than one designated server or P2P call routing.
 3. The method of claim 1 wherein determining of call routing include determining routing path based call session quality parameters.
 4. The method of claim 1 wherein determining of call routing include determining call type
 5. The method of claim 3 wherein the quality parameters are tested using organization servers or cloud servers. (Consulting with peer offices/cloud servers).
 6. The method of claim 1 further comprising the step of determining additional actions including at least one of: monitoring, recording or encrypting of call session by at least one designated network server.
 7. The method of claim 1 wherein the meta data include at least one of: requesting user profile, requesting user device characteristics, connectivity profile or network quality.
 8. The method of claim 1 wherein the location identification is based on retrieving data of past interactions of user requests in short time period, in case of identifying call request as continuation of previous call maintaining the same routing method and path.
 9. The method of claim 2 wherein in case of local routing the routing is based on office location using a single network sever.
 10. The method of claim 2 wherein in case of non-local routing the routing is based on user location using more than one network server.
 11. A system for routing a call initiated by at least one user of an organization having at least one communication server for handling the call routing, wherein the organization communication server are located at different geographical areas, said system is comprised of: Location identifying module for identifying geographical and logical location of requesting member based on received meta data; Authorizing module for authorizing call based on determined location, metadata by applying organization policy; and Routing decision module for determining call routing method based on location data and metadata by applying pre-defined organization policies rules.
 12. The system of claim 9 wherein the call routing method is at least one of: local routing using single designated network server, non-local routing using more than one server or P2P call routing.
 13. The system of claim 11 wherein determining of call routing include determining routing path based call session quality parameters.
 14. The system of claim 11 wherein determining of call routing include determine call type.
 15. The system of claim 13 wherein the quality parameters are tested using organization servers or cloud servers. (Consulting with peer offices/cloud servers).
 16. The system of claim 11 wherein routing decision module further determine actions to be taken in relation to the call including at least one of: monitoring, recording or encrypting of call session by at least one network server.
 17. The system of claim 11 wherein the location identification is based on Retrieving data of past interactions of user requests in short time period, in-case of detecting the new call request is a continuation of previous call maintaining the same routing method and path.
 18. The system of claim 12 wherein in case of local routing the routing is based on office location using a single network sever.
 19. The system of claim 12 wherein in case of non local routing the routing is based on user location using more than one network server. 